Hi jwalton,

first of all thank you for the recent collaboration on requireish. It was really fun and productive ;)

I wanted to implement the new functionality in my project and faced new problems. I generally think, that it is not a good idea to replace the aliases with relative paths. There is no argument against replacing them always with absolute ones.

This was very crucial when I tried to use proxyquierifywith aliasify. Let me explain the scenario:
With proxyquireify you are able to stub out arbitrary required modules. The problem here is... If you require a module through an alias in the original file which gehts replaced through a relative path from aliasify you are not longer able to stub out this package because the require path for that module was manipulated and can not longer be stubbed out with the alias.

Here comes a second problem in play. There is no method to manually get the replacement for an alias. I have to programmatically get the replacement path for the alias I want to stub out what is now possible with the new method getReplacement.

Now the absolute paths are important because the stubbed out path in the proxyquireify stubs has to match the replaced require path in the original file. This is nearly impossible if you have your spec files in a completely different folder than your src files.

Last but not least I updated the README with the new functionalities and edited the requireish part which was not exactly correct.